neuron Carrier Experience API
Environments
The Neuron Carrier Experience API is available across multiple environments to support development, testing, and live trading operations. Each environment has its own base URL, credentials, and data behaviour.
This page explains how to use them and what to expect when integrating.
π§ͺ UAT Environment
The UAT environment is intended for development, integration testing, and validation before moving to production.
πΉ Purpose
- Test authentication and API connectivity
- Validate payloads and response structures
- Run end-to-end integration scenarios
- Safely test without impacting live data
πΉ Base URL
https://api.uat.neurondigitaltrading.com/carrier/{version}πΉ Notes
- Data is non-production and refreshed periodically
- Performance characteristics may differ from production
client_idand JWT values are environment-specific
π Production Environment
The Production environment is the live, operational system used for real broker submissions and carrier responses.
πΉ Purpose
- Live trading activity
- Real-time submission and quote processing
- High-availability, high-performance operations
πΉ Base URL
https://api.neurondigitaltrading.com/carrier/{version}πΉ Notes
- Only onboarded, approved integrations should call production
- All requests must be authenticated using production-issued credentials
- Payload validation and error handling are strict to protect data quality
π Environment-Specific Credentials
Each environment requires its own:
client_id- JWT (Azure AD) configuration
- Allowed redirect URIs (if applicable)
- Access roles
Ensure you request the correct credentials when onboarding.
π What to Expect Across Environments
| Aspect | UAT | Production |
|---|---|---|
| Data | Test data | Real broker submissions |
| Credentials | UAT-specific | Production-specific |
| Rate Limits | Standard test limits | Operational limits |
| Error Behaviour | Relaxed for debugging | Strict validation |
| Usage | Integration & QA | Live trading |